[flake8-simplify] Fix SIM222 false positive for tuple(generator) or None (SIM222)#21187
Merged
MichaReiser merged 3 commits intoastral-sh:mainfrom Nov 10, 2025
Merged
[flake8-simplify] Fix SIM222 false positive for tuple(generator) or None (SIM222)#21187MichaReiser merged 3 commits intoastral-sh:mainfrom
flake8-simplify] Fix SIM222 false positive for tuple(generator) or None (SIM222)#21187MichaReiser merged 3 commits intoastral-sh:mainfrom
Conversation
Contributor
|
ntBre
added
bug
ntBre
reviewed
Nov 3, 2025
| // is falsy. | ||
| if matches!( | ||
| &arguments.args[0], | ||
| Expr::Generator(_) | Expr::ListComp(_) | Expr::SetComp(_) |
Contributor
There was a problem hiding this comment.
I think this only needs to include Generator, not the comprehension types. Recursing into the Self::from_expr arm below should already return Self::Unknown for other comprehensions. Generators are the only special case on 1223, if I'm following correctly.
The last two new tests already suppress the rule, for example: https://play.ruff.rs/a211c51a-b6f3-4dae-b259-431a75788464
MichaReiser
approved these changes
Nov 10, 2025
dcreager
added a commit
that referenced
this pull request
Nov 11, 2025
* origin/main: (38 commits) [ty] Make implicit submodule imports only occur in global scope (#21370) [ty] introduce local variables for `from` imports of submodules in `__init__.py(i)` (#21173) [`ruff`] Ignore `str()` when not used for simple conversion (`RUF065`) (#21330) [ty] implement `typing.NewType` by adding `Type::NewTypeInstance` [ty] supress inlay hints for `+1` and `-1` (#21368) [ty] Use type context for inference of generic constructors (#20933) [ty] Improve generic call expression inference (#21210) [ty] supress some trivial expr inlay hints (#21367) [`configuration`] Fix unclear error messages for line-length values exceeding `u16::MAX` (#21329) [ty] Fix incorrect inference of `enum.auto()` for enums with non-`int` mixins, and imprecise inference of `enum.auto()` for single-member enums (#20541) [`refurb`] Detect empty f-strings (`FURB105`) (#21348) [ty] provide `import` completion when in `from <name> <name>` statement (#21291) [ty] elide redundant inlay hints for function args (#21365) Fix syntax error false positive on alternative `match` patterns (#21362) Add a new "Opening a PR" section to the contribution guide (#21298) [`flake8-simplify`] Fix SIM222 false positive for `tuple(generator) or None` (`SIM222`) (#21187) Rebuild ruff binary instead of sharing it across jobs (#21361) [ty] Fix `--exclude` and `src.exclude` merging (#21341) [ty] Add support for properties that return `Self` (#21335) Add upstream linter URL to `ruff linter --output-format=json` (#21316) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #21136. The rule was incorrectly treating
tuple(generator)as always truthy, buttuple(empty_generator)is falsy.Problem Analysis
SIM222 was incorrectly suggesting to remove
or Nonefromtuple(item for item in items) or Nonebecause it was treating the tuple call as always truthy. However, when a generator expression is empty,tuple(empty_generator)produces an empty tuple(), which is falsy. Removingor Nonewould change the runtime behavior.Approach
Updated
Truthiness::from_exprto returnUnknownfortuple(generator),tuple(list_comp), andtuple(set_comp)calls, since we cannot statically determine if the resulting tuple will be empty or not. This prevents SIM222 from flagging these cases incorrectly.